iKnowMed Cloud Migration FAQ Copied
Ontada is modernizing iKnowMed Generation 2 by moving it to the cloud in January 2026. This strategic migration:
- Supports current user activity demands and future capacity.
- Allows our team to easily access robust technology and tools for future development.
- Be more adaptable to evolving practice needs.
- Makes it easier to recover in the event of a disaster.
Following a planned iKnowMed update on Saturday, Oct. 11, 2025, we have paused releasing new features and functionality. From October through January, we’ll continue developing new features and functionality to be released after the migration is complete.
The cloud migration will require an extended maintenance window, where iKnowMed, iKnowMed Mobile, and other Ontada applications will be unavailable. The iKnowMed Read Only environment will be available during the extended maintenance window.
While the team is finalizing the migration schedule and details, we know the migration will begin on Saturday, Jan. 24, 2026, and will be completed on Sunday, Jan. 25, 2026, in advance of Monday’s business hours. Once the schedule and times are finalized, we’ll share those details with practices.
What does moving to the cloud mean for iKnowMed?
Moving iKnowMed to the cloud means transitioning iKnowMed systems from McKesson managed data centers to Microsoft Azure cloud. This shift allows iKnowMed to run on secure, scalable servers managed by trusted cloud partners, rather than relying on local data centers or hardware.
Why can’t you release new functionality and migrate to the cloud?
Due to the time of year, Ontada typically tries to avoid releasing updates during the holiday season. We know staff at your practices take time off and this season isn’t an optimal time to introduce change.
Additionally, we want to minimize change within iKnowMed while migrating the underlying infrastructure. This allows our team to have a singular focus, while limiting disruption for users at your practice.
Following the migration, the next iKnowMed release is slated for February 2026.
Other products within the Ontada portfolio, like Clear Value Plus, Ontada Health Patient Portal and e-Registration, and Practice Insights will continue releasing during this time.
Why is Ontada doing this?
- Scalability: Azure provides elastic scalability that supports current users and future growth ensuring our infrastructure can handle increasing workloads, user traffic, and data volumes.
- Advanced Tools and Services: Access to a wide range of cutting-edge services—from AI and analytics to deployment automation, enabling us to deliver new features faster and build solutions that are more secure, efficient, and resilient.
- System Resiliency: Provides a foundation which helps us minimize downtime and recover quickly in the event of an outage—keeping data safe and services available when you need them most.
- High Performance Database Hardware: Oracle Exadata (on Azure) allows us to deliver faster, more reliable applications by leveraging high-performance database hardware optimized for enterprise workloads.
What does this mean for my practice?
Your practice should experience zero impact, beyond the extended maintenance window in January for the migration. Users should see no difference when they log out before the migration, and when they log in after the migration. Nothing in iKnowMed will have changed.
When will the migration to the cloud start?
The teams have already started the migration. Moving smaller, less critical aspects of our technology. Between now and January, the team will continue completing iterative preparation and work. In January, the final database migration activities will take place leaving us with a fully cloud based iKnowMed application.
When will the cloud migration be finished?
Our team is currently finalizing our testing plans to inform when the migration can be scheduled in January. We will provide advanced notification so practices can plan accordingly.
Will Read Only be available during the cloud migration?
Yes. The Read Only environment will be accessible during the maintenance window to review patient data.
Will other Ontada applications be impacted during the migration maintenance window?
During maintenance, iKnowMed Mobile, iKnowMed Patient Viewer, and the Ontada Health Patient Portal will be unavailable.
Patients completing forms through Ontada Health e-Registration will not see pre-populated information like known pharmacy, medications, and allergy information. Data submitted through forms will be queued until after maintenance is complete and added to the patient chart. Integrated data such as pharmacy, medications, and allergy information will not be automatically added to the chart and will need to be manually entered.
Patients using the Navigating Care patient portal will be able to access information that was entered prior to the maintenance window. Information entered during maintenance will be available following the Navigating Cancer patient data update the following evening.
The Clear Value Plus Administration Portal will continue to be available. However, iKnowMed Generation 2 users will not be able to create new decisions until maintenance is complete. You will still be able to review existing decisions and data.
Other McKesson and Ontada Technology Solutions applications will be available during this time.
How is Ontada supporting practices after the migration?
Following the migration, Ontada teams will be monitoring the system to ensure a seamless experience for practices. Hypercare monitoring of performance, stability and health metrics will continue for three weeks.
What can users expect after the migration?
User experience workflows will not change. Previous behaviors and defects will still be present.
Will there be a new way to access iKnowMed?
No, you’ll continue to access iKnowMed as you always have. There won’t be a new URL or new login experience.
Can practices expect changes to release downtimes and events following the migration?
No, release processes and downtime will remain the same. Migrating to Microsoft Azure cloud opens possibilities for future optimizations, backup application access, and reduced release downtimes, which we will explore in 2026. Any changes in the future will be communicated in advance.
Development of new functionality will continue during the migration preparation and deployment. Does this mean users can expect more in the February release?
The February release will contain new features and defect corrections that are developed and tested internally between October 2025 and January 2026. Typical release timelines include eight weeks of development and testing; the February release will contain changes developed across sixteen weeks.
